Actuator enclosure assembly

ABSTRACT

An actuator is usable in an airside system, waterside system, building management system, or HVAC system. The actuator includes a housing. The housing includes an enclosure having an interior surface with a channel. The channel includes a ledge portion. The channel extends through the enclosure. The actuator includes a yoke having a notch located on an external surface of the yoke. The actuator includes a locking mechanism including a ring having a tab. The tab is defined by a width of the channel and a width of the notch. Following assembly, the yoke is positioned in the enclosure such that the notch rests upon the ledge portion. Additionally, the locking mechanism is positioned on an opposite side of the enclosure with the tab positioned in the channel adjacent to the notch. As a result, the locking mechanism inhibits movement of the yoke relative to the enclosure.

BACKGROUND

The present disclosure relates generally to actuators in a heating,ventilating, or air conditioning (HVAC) system and more particularly toassembly of an enclosure for an actuator that may be used in HVAC orsimilar systems.

HVAC actuators are used to operate a wide variety of HVAC components,such as air dampers, fluid valves, air handling units, and othercomponents that are typically used in HVAC systems. For example, anactuator may be coupled to a damper in an HVAC system and may be used todrive the damper between an open position and a closed position. An HVACactuator typically includes a motor and a yoke (e.g., a hub, a drivetrain, drive device, etc.) that is driven by the motor and coupled tothe HVAC component.

Typical HVAC actuators use snap joints for assembly. These snap jointsare typically permanent fixtures that are designed to sustain thrustload from the motor during actuator operation. Given the permanentnature of these snap joints, disassembly is difficult without breakingthese snap joints. Some HVAC actuators have an integral yoke. However,these yokes may break during coupling to the movable HVAC component.

SUMMARY

At least one embodiment relates to an actuator. The actuator includes anenclosure having an interior surface including a channel with a ledgeportion extending through the enclosure. The actuator includes a yokehaving a notch located on an external surface, the yoke positioned inthe enclosure with the notch resting on the ledge portion of theenclosure. The actuator includes a locking mechanism including a ringhaving a tab with a width corresponding to a width of the channel and awidth of the notch. The locking mechanism is positioned on an oppositeside of the enclosure with the tab positioned in the channel adjacent tothe notch and thereby inhibiting reverse rotation of the yoke.

In some embodiments, the actuator may be a rotary actuator.

In some embodiments, the actuator may be a linear actuator.

In some embodiments, the plurality of channels are radially arrangedabout the enclosure.

In some embodiments, the width of the channel at the ledge portion isequal to, at least, the width of the width of the tab and the width ofthe notch.

In some embodiments, the yoke is inserted in the enclosure with thenotch at the narrow portion and pushed to the wide portion. The yoke maybe rotated when the notch is located at the wide portion to rest uponthe ledge portion.

In some embodiments, the locking mechanism is inserted with the tab atthe wide portion where the tab is located adjacent to the notch.

At least one embodiment relates to an actuator. The actuator includes ahousing including an enclosure having an interior surface including aplurality of channels with corresponding ledge portions. The pluralityof channels extend through the enclosure. The actuator includes a yokehaving a plurality of notches located on an external surface. The yokeis positioned in the enclosure with the notches resting on respectiveledge portions of the enclosure. The actuator includes a lockingmechanism including a ring having a plurality of tabs with a widthdefined by a width of the channel and a width of the notch. The lockingmechanism is positioned on an opposite side of the enclosure with thetabs positioned in respective channels adjacent to respective notchesand thereby inhibiting reverse rotation of the yoke.

In some embodiments, the actuator is a rotary actuator.

In some embodiments, the actuator is a linear actuator.

In some embodiments, the plurality of channels are radially arrangedabout the enclosure.

In some embodiments, the width of the channels at the ledge portion isequal to, at least, the width of the width of the tabs and the width ofthe notches.

In some embodiments, the channels have a narrow portion and a wideportion. The ledge portion may be located within the wide portion of thechannel.

In some embodiments, the yoke is inserted in the enclosure with thenotches at the narrow portion and pushed to the wide portion. The yokemay be rotated when the notches are located at the wide portion to restupon the ledge.

In some embodiments, the locking mechanism is inserted with the tabs atthe wide portion where the tabs located adjacent to the notch.

At least one embodiment relates to a method of assembling an actuator.The method includes inserting a yoke into a first opening of anenclosure for an actuator. The enclosure includes an interior surfacehaving a channel with a ledge portion extending through the enclosure.The yoke has a notch on an external surface facing the channel when theyoke is inserted into the first opening. The method includes rotatingthe yoke such that the notch rests on the ledge portion of theenclosure. The method includes inserting a locking mechanism into asecond opening of the enclosure. The locking mechanism includes a tabhaving a width corresponding to a width of the channel and a width ofthe notch. The tab is positioned in the channel adjacent to the notchthereby inhibiting movement of the yoke with respect to the enclosure.

In some embodiments, the channel has a narrow portion and a wide portionwith the ledge portion being located within the wide portion of thechannel. Inserting the yoke into the first opening may include insertingthe yoke into the first opening of the enclosure for the actuatoradjacent to the narrow portion. Inserting the yoke into the firstopening may further include pushing the yoke into the enclosure suchthat the notch moves from the narrow portion to the wide portion. Theyoke may be rotated when the notch is located within the wide portion.

In some embodiments, the locking mechanism is inserted with the tab atthe wide portion where the tab is located adjacent to the notch.

This summary is illustrative only and is not intended to be in any waylimiting. Other aspects, inventive features, and advantages of thedevices or processes described herein will become apparent in thedetailed description set forth herein, taken in conjunction with theaccompanying figures, wherein like reference numerals refer to likeelements.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a drawing of a building equipped with a heating, ventilating,or air conditioning (HVAC) system and a building management system(BMS), according to an exemplary embodiment.

FIG. 2 is a schematic diagram of a waterside system which may be used tosupport the HVAC system of FIG. 1, according to an exemplary embodiment.

FIG. 3 is a block diagram of an airside system which may be used as partof the HVAC system of FIG. 1, according to an exemplary embodiment.

FIG. 4 is a block diagram of a BMS which may be implemented in thebuilding of FIG. 1, according to an exemplary embodiment.

FIG. 5 is a view of an actuator which may be used in the HVAC system ofFIG. 1, the waterside system of FIG. 2, the airside system of FIG. 3, orthe BMS of FIG. 4 to control an HVAC component, according to anexemplary embodiment.

FIG. 6 is a view of an enclosure for a housing of the actuator of FIG.5, according to an exemplary embodiment.

FIG. 7 is a view of a portion of the enclosure 510 of FIG. 6, accordingto an exemplary embodiment.

FIG. 8A and FIG. 8B show example yokes for the actuator of FIG. 5,according to an exemplary embodiment.

FIG. 9 shows a view of a locking mechanism for the enclosure of FIG. 6,according to an exemplary embodiment.

FIG. 10 shows an exploded view of an assembly of the yoke of FIG. 8A,the enclosure of FIG. 6, and the locking mechanism of FIG. 9, accordingto an exemplary embodiment.

FIG. 11 is a flowchart of a process of assembling the HVAC actuator ofFIG. 5, according to an exemplary embodiment.

FIG. 12A and FIG. 12B show cross-sectional views of the HVAC actuator ofFIG. 5 assembled with the yoke of FIG. 8A and FIG. 8B and the lockingmechanism of FIG. 9, according to exemplary embodiments.

DETAILED DESCRIPTION

Before turning to the figures, which illustrate certain exemplaryembodiments in detail, it should be understood that the presentdisclosure is not limited to the details or methodology set forth in thedescription or illustrated in the figures. It should also be understoodthat the terminology used herein is for the purpose of description onlyand should not be regarded as limiting.

Referring generally to the FIGURES, an HVAC actuator is shown, accordingto an exemplary embodiment. The actuator may be a damper actuator, avalve actuator, a fan actuator, a pump actuator, or any other type ofactuator that can be used in an HVAC or other system.

The actuator includes a housing. The housing includes an enclosurehaving an interior surface with a channel. The channel includes a ledgeportion. The channel extends through the enclosure. The actuatorincludes a yoke having a notch located on an external surface of theyoke. The actuator includes a locking mechanism including a ring havinga tab. The tab is defined by a width of the channel and a width of thenotch.

Following assembly, the yoke is positioned in the enclosure such thatthe notch rests upon the ledge portion. Additionally, the lockingmechanism is positioned on an opposite side of the enclosure with thetab positioned in the channel adjacent to the notch. As a result, thelocking mechanism inhibits movement of the yoke relative to theenclosure.

The aspects described herein may decrease the cost and time of assemblythrough use of the locking mechanism. Additionally, the enclosure may beshaped to receive different types of yokes, thereby increasinguniversality and decreasing design costs. The aspects described hereinmay decrease the likelihood of any components breaking duringdisassembly. Various other benefits of the present disclosure willbecome apparent as follows.

Building Management System and HVAC System

Referring now to FIGS. 1-4, an exemplary building management system(BMS) and HVAC system in which the systems and methods of the presentdisclosure may be implemented are shown, according to an exemplaryembodiment. Referring particularly to FIG. 1, a perspective view of abuilding 10 is shown. Building 10 is served by a BMS. A BMS is, ingeneral, a system of devices configured to control, monitor, and manageequipment in or around a building or building area. A BMS may include,for example, an HVAC system, a security system, a lighting system, afire alerting system, any other system that is capable of managingbuilding functions or devices, or any combination thereof.

The BMS that serves building 10 includes an HVAC system 100. HVAC system100 may include a plurality of HVAC devices (e.g., heaters, chillers,air handling units, pumps, fans, thermal energy storage, etc.)configured to provide heating, cooling, ventilation, or other servicesfor building 10. For example, HVAC system 100 is shown to include awaterside system 120 and an airside system 130. Waterside system 120 mayprovide heated or chilled fluid to an air handling unit of airsidesystem 130. Airside system 130 may use the heated or chilled fluid toheat or cool an airflow provided to building 10. An exemplary watersidesystem and airside system which may be used in HVAC system 100 aredescribed in greater detail with reference to FIGS. 2-3.

HVAC system 100 is shown to include a chiller 102, a boiler 104, and arooftop air handling unit (AHU) 106. Waterside system 120 may use boiler104 and chiller 102 to heat or cool a working fluid (e.g., water,glycol, etc.) and may circulate the working fluid to AHU 106. In variousembodiments, the HVAC devices of waterside system 120 may be located inor around building 10 (as shown in FIG. 1) or at an offsite locationsuch as a central plant (e.g., a chiller plant, a steam plant, a heatplant, etc.). The working fluid may be heated in boiler 104 or cooled inchiller 102, depending on whether heating or cooling is required inbuilding 10. Boiler 104 may add heat to the circulated fluid, forexample, by burning a combustible material (e.g., natural gas) or usingan electric heating element. Chiller 102 may place the circulated fluidin a heat exchange relationship with another fluid (e.g., a refrigerant)in a heat exchanger (e.g., an evaporator) to absorb heat from thecirculated fluid. The working fluid from chiller 102 and/or boiler 104may be transported to AHU 106 via piping 108.

AHU 106 may place the working fluid in a heat exchange relationship withan airflow passing through AHU 106 (e.g., via one or more stages ofcooling coils and/or heating coils). The airflow may be, for example,outside air, return air from within building 10, or a combination ofboth. AHU 106 may transfer heat between the airflow and the workingfluid to provide heating or cooling for the airflow. For example, AHU106 may include one or more fans or blowers configured to pass theairflow over or through a heat exchanger containing the working fluid.The working fluid may then return to chiller 102 or boiler 104 viapiping 110.

Airside system 130 may deliver the airflow supplied by AHU 106 (i.e.,the supply airflow) to building 10 via air supply ducts 112 and mayprovide return air from building 10 to AHU 106 via air return ducts 114.In some embodiments, airside system 130 includes multiple variable airvolume (VAV) units 116. For example, airside system 130 is shown toinclude a separate VAV unit 116 on each floor or zone of building 10.VAV units 116 may include dampers or other flow control elements thatmay be operated to control an amount of the supply airflow provided toindividual zones of building 10. In other embodiments, airside system130 delivers the supply airflow into one or more zones of building 10(e.g., via supply ducts 112) without using intermediate VAV units 116 orother flow control elements. AHU 106 may include various sensors (e.g.,temperature sensors, pressure sensors, etc.) configured to measureattributes of the supply airflow. AHU 106 may receive input from sensorslocated within AHU 106 and/or within the building zone and may adjustthe flow rate, temperature, or other attributes of the supply airflowthrough AHU 106 to achieve set point conditions for the building zone.

Referring now to FIG. 2, a block diagram of a waterside system 200 isshown, according to an exemplary embodiment. In various embodiments,waterside system 200 may supplement or replace waterside system 120 inHVAC system 100 or may be implemented separate from HVAC system 100.When implemented in HVAC system 100, waterside system 200 may include asubset of the HVAC devices in HVAC system 100 (e.g., boiler 104, chiller102, pumps, valves, etc.) and may operate to supply a heated or chilledfluid to AHU 106. The HVAC devices of waterside system 200 may belocated within building 10 (e.g., as components of waterside system 120)or at an offsite location such as a central plant.

In FIG. 2, waterside system 200 is shown as a central plant having aplurality of subplants 202-212. Subplants 202-212 are shown to include aheater subplant 202, a heat recovery chiller subplant 204, a chillersubplant 206, a cooling tower subplant 208, a hot thermal energy storage(TES) subplant 210, and a cold thermal energy storage (TES) subplant212. Subplants 202-212 consume resources (e.g., water, natural gas,electricity, etc.) from utilities to serve the thermal energy loads(e.g., hot water, cold water, heating, cooling, etc.) of a building orcampus. For example, heater subplant 202 may be configured to heat waterin a hot water loop 214 that circulates the hot water between heatersubplant 202 and building 10. Chiller subplant 206 may be configured tochill water in a cold water loop 216 that circulates the cold waterbetween chiller subplant 206 and building 10. Heat recovery chillersubplant 204 may be configured to transfer heat from cold water loop 216to hot water loop 214 to provide additional heating for the hot waterand additional cooling for the cold water. Condenser water loop 218 mayabsorb heat from the cold water in chiller subplant 206 and reject theabsorbed heat in cooling tower subplant 208 or transfer the absorbedheat to hot water loop 214. Hot TES subplant 210 and cold TES subplant212 may store hot and cold thermal energy, respectively, for subsequentuse.

Hot water loop 214 and cold water loop 216 may deliver the heated and/orchilled water to air handlers located on the rooftop of building 10(e.g., AHU 106) or to individual floors or zones of building 10 (e.g.,VAV units 116). The air handlers push air past heat exchangers (e.g.,heating coils or cooling coils) through which the water flows to provideheating or cooling for the air. The heated or cooled air may bedelivered to individual zones of building 10 to serve the thermal energyloads of building 10. The water then returns to subplants 202-212 toreceive further heating or cooling.

Although subplants 202-212 are shown and described as heating andcooling water for circulation to a building, it is understood that anyother type of working fluid (e.g., glycol, CO2, etc.) may be used inplace of or in addition to water to serve the thermal energy loads. Inother embodiments, subplants 202-212 may provide heating and/or coolingdirectly to the building or campus without requiring an intermediateheat transfer fluid. These and other variations to waterside system 200are within the teachings of the present disclosure.

Each of subplants 202-212 may include a variety of equipment configuredto facilitate the functions of the subplant. For example, heatersubplant 202 is shown to include a plurality of heating elements 220(e.g., boilers, electric heaters, etc.) configured to add heat to thehot water in hot water loop 214. Heater subplant 202 is also shown toinclude several pumps 222 and 224 configured to circulate the hot waterin hot water loop 214 and to control the flow rate of the hot waterthrough individual heating elements 220. Chiller subplant 206 is shownto include a plurality of chillers 232 configured to remove heat fromthe cold water in cold water loop 216. Chiller subplant 206 is alsoshown to include several pumps 234 and 236 configured to circulate thecold water in cold water loop 216 and to control the flow rate of thecold water through individual chillers 232.

Heat recovery chiller subplant 204 is shown to include a plurality ofheat recovery heat exchangers 226 (e.g., refrigeration circuits)configured to transfer heat from cold water loop 216 to hot water loop214. Heat recovery chiller subplant 204 is also shown to include severalpumps 228 and 230 configured to circulate the hot water and/or coldwater through heat recovery heat exchangers 226 and to control the flowrate of the water through individual heat recovery heat exchangers 226.Cooling tower subplant 208 is shown to include a plurality of coolingtowers 238 configured to remove heat from the condenser water incondenser water loop 218. Cooling tower subplant 208 is also shown toinclude several pumps 240 configured to circulate the condenser water incondenser water loop 218 and to control the flow rate of the condenserwater through individual cooling towers 238.

Hot TES subplant 210 is shown to include a hot TES tank 242 configuredto store the hot water for later use. Hot TES subplant 210 may alsoinclude one or more pumps or valves configured to control the flow rateof the hot water into or out of hot TES tank 242. Cold TES subplant 212is shown to include cold TES tanks 244 configured to store the coldwater for later use. Cold TES subplant 212 may also include one or morepumps or valves configured to control the flow rate of the cold waterinto or out of cold TES tanks 244.

In some embodiments, one or more of the pumps in waterside system 200(e.g., pumps 222, 224, 228, 230, 234, 236, and/or 240) or pipelines inwaterside system 200 include an isolation valve associated therewith.Isolation valves may be integrated with the pumps or positioned upstreamor downstream of the pumps to control the fluid flows in watersidesystem 200. In various embodiments, waterside system 200 may includemore, fewer, or different types of devices and/or subplants based on theparticular configuration of waterside system 200 and the types of loadsserved by waterside system 200.

Referring now to FIG. 3, a block diagram of an airside system 300 isshown, according to an exemplary embodiment. In various embodiments,airside system 300 may supplement or replace airside system 130 in HVACsystem 100 or may be implemented separate from HVAC system 100. Whenimplemented in HVAC system 100, airside system 300 may include a subsetof the HVAC devices in HVAC system 100 (e.g., AHU 106, VAV units 116,ducts 112-114, fans, dampers, etc.) and may be located in or aroundbuilding 10. Airside system 300 may operate to heat or cool an airflowprovided to building 10 using a heated or chilled fluid provided bywaterside system 200.

In FIG. 3, airside system 300 is shown to include an economizer-type AHU302. Economizer-type AHUs vary the amount of outside air and return airused by the air handling unit for heating or cooling. For example, AHU302 may receive return air 304 from building zone 306 via return airduct 308 and may deliver supply air 310 to building zone 306 via supplyair duct 312. In some embodiments, AHU 302 is a rooftop unit located onthe roof of building 10 (e.g., AHU 106 as shown in FIG. 1) or otherwisepositioned to receive both return air 304 and outside air 314. AHU 302may be configured to operate exhaust air damper 316, mixing damper 318,and outside air damper 320 to control an amount of outside air 314 andreturn air 304 that combine to form supply air 310. Any return air 304that does not pass through mixing damper 318 may be exhausted from AHU302 through exhaust damper 316 as exhaust air 322.

Each of dampers 316-320 may be operated by an actuator. For example,exhaust air damper 316 may be operated by actuator 324, mixing damper318 may be operated by actuator 326, and outside air damper 320 may beoperated by actuator 328. Actuators 324-328 may communicate with an AHUcontroller 330 via a communications link 332. Actuators 324-328 mayreceive control signals from AHU controller 330 and may provide feedbacksignals to AHU controller 330. Feedback signals may include, forexample, an indication of a current actuator or damper position, anamount of torque or force exerted by the actuator, diagnosticinformation (e.g., results of diagnostic tests performed by actuators324-328), status information, commissioning information, configurationsettings, calibration data, and/or other types of information or datathat may be collected, stored, or used by actuators 324-328. AHUcontroller 330 may be an economizer controller configured to use one ormore control algorithms (e.g., state-based algorithms, extremum seekingcontrol (ESC) algorithms, proportional-integral (PI) control algorithms,proportional-integral-derivative (PID) control algorithms, modelpredictive control (MPC) algorithms, feedback control algorithms, etc.)to control actuators 324-328.

Still referring to FIG. 3, AHU 302 is shown to include a cooling coil334, a heating coil 336, and a fan 338 positioned within supply air duct312. Fan 338 may be configured to force supply air 310 through coolingcoil 334 and/or heating coil 336 and provide supply air 310 to buildingzone 306. AHU controller 330 may communicate with fan 338 viacommunications link 340 to control a flow rate of supply air 310. Insome embodiments, AHU controller 330 controls an amount of heating orcooling applied to supply air 310 by modulating a speed of fan 338.

Cooling coil 334 may receive a chilled fluid from waterside system 200(e.g., from cold water loop 216) via piping 342 and may return thechilled fluid to waterside system 200 via piping 344. Valve 346 may bepositioned along piping 342 or piping 344 to control a flow rate of thechilled fluid through cooling coil 334. In some embodiments, coolingcoil 334 includes multiple stages of cooling coils that may beindependently activated and deactivated (e.g., by AHU controller 330, byBMS controller 366, etc.) to modulate an amount of cooling applied tosupply air 310.

Heating coil 336 may receive a heated fluid from waterside system 200(e.g., from hot water loop 214) via piping 348 and may return the heatedfluid to waterside system 200 via piping 350. Valve 352 may bepositioned along piping 348 or piping 350 to control a flow rate of theheated fluid through heating coil 336. In some embodiments, heating coil336 includes multiple stages of heating coils that may be independentlyactivated and deactivated (e.g., by AHU controller 330, by BMScontroller 366, etc.) to modulate an amount of heating applied to supplyair 310.

Each of valves 346 and 352 may be controlled by an actuator. Forexample, valve 346 may be controlled by actuator 354 and valve 352 maybe controlled by actuator 356. Actuators 354-356 may communicate withAHU controller 330 via communications links 358-360. Actuators 354-356may receive control signals from AHU controller 330 and may providefeedback signals to controller 330. In some embodiments, AHU controller330 receives a measurement of the supply air temperature from atemperature sensor 362 positioned in supply air duct 312 (e.g.,downstream of cooling coil 334 and/or heating coil 336). AHU controller330 may also receive a measurement of the temperature of building zone306 from a temperature sensor 364 located in building zone 306.

In some embodiments, AHU controller 330 operates valves 346 and 352 viaactuators 354-356 to modulate an amount of heating or cooling providedto supply air 310 (e.g., to achieve a setpoint temperature for supplyair 310 or to maintain the temperature of supply air 310 within asetpoint temperature range). The positions of valves 346 and 352 affectthe amount of heating or cooling provided to supply air 310 by coolingcoil 334 or heating coil 336 and may correlate with the amount of energyconsumed to achieve a desired supply air temperature. AHU controller 330may control the temperature of supply air 310 and/or building zone 306by activating or deactivating coils 334-336, adjusting a speed of fan338, or a combination of both.

Still referring to FIG. 3, airside system 300 is shown to include a BMScontroller 366 and a client device 368. BMS controller 366 may includeone or more computer systems (e.g., servers, supervisory controllers,subsystem controllers, etc.) that serve as system-level controllers,application or data servers, head nodes, or master controllers forairside system 300, waterside system 200, HVAC system 100, and/or othercontrollable systems that serve building 10. BMS controller 366 maycommunicate with multiple downstream building systems or subsystems(e.g., HVAC system 100, a security system, a lighting system, watersidesystem 200, etc.) via a communications link 370 according to like ordisparate protocols (e.g., LON, BACnet, etc.). In various embodiments,AHU controller 330 and BMS controller 366 may be separate (as shown inFIG. 3) or integrated. In an integrated implementation, AHU controller330 may be a software module configured for execution by a processor ofBMS controller 366.

In some embodiments, AHU controller 330 receives information from BMScontroller 366 (e.g., commands, setpoints, operating boundaries, etc.)and provides information to BMS controller 366 (e.g., temperaturemeasurements, valve or actuator positions, operating statuses,diagnostics, etc.). For example, AHU controller 330 may provide BMScontroller 366 with temperature measurements from temperature sensors362-364, equipment on/off states, equipment operating capacities, and/orany other information that may be used by BMS controller 366 to monitoror control a variable state or condition within building zone 306.

Client device 368 may include one or more human-machine interfaces orclient interfaces (e.g., graphical user interfaces, reportinginterfaces, text-based computer interfaces, client-facing web services,web servers that provide pages to web clients, etc.) for controlling,viewing, or otherwise interacting with HVAC system 100, its subsystems,and/or devices. Client device 368 may be a computer workstation, aclient terminal, a remote or local interface, or any other type of userinterface device. Client device 368 may be a stationary terminal or amobile device. For example, client device 368 may be a desktop computer,a computer server with a user interface, a laptop computer, a tablet, asmartphone, a PDA, or any other type of mobile or non-mobile device.Client device 368 may communicate with BMS controller 366 and/or AHUcontroller 330 via communications link 372.

Referring now to FIG. 4, a block diagram of a BMS 400 is shown,according to an exemplary embodiment. BMS 400 may be implemented inbuilding 10 to automatically monitor and control various buildingfunctions. BMS 400 is shown to include BMS controller 366 and aplurality of building subsystems 428. Building subsystems 428 are shownto include a building electrical subsystem 434, an informationcommunication technology (ICT) subsystem 436, a security subsystem 438,an HVAC subsystem 440, a lighting subsystem 442, a lift/escalatorssubsystem 432, and a fire safety subsystem 430. In various embodiments,building subsystems 428 may include fewer, additional, or alternativesubsystems. For example, building subsystems 428 may also oralternatively include a refrigeration subsystem, an advertising orsignage subsystem, a cooking subsystem, a vending subsystem, a printeror copy service subsystem, or any other type of building subsystem thatuses controllable equipment and/or sensors to monitor or controlbuilding 10. In some embodiments, building subsystems 428 includewaterside system 200 and/or airside system 300, as described withreference to FIGS. 2-3.

Each of building subsystems 428 may include any number of devices,controllers, and connections for completing its individual functions andcontrol activities. HVAC subsystem 440 may include many of the samecomponents as HVAC system 100, as described with reference to FIGS. 1-3.For example, HVAC subsystem 440 may include any number of chillers,heaters, handling units, economizers, field controllers, supervisorycontrollers, actuators, temperature sensors, and/or other devices forcontrolling the temperature, humidity, airflow, or other variableconditions within building 10. Lighting subsystem 442 may include anynumber of light fixtures, ballasts, lighting sensors, dimmers, or otherdevices configured to controllably adjust the amount of light providedto a building space. Security subsystem 438 may include occupancysensors, video surveillance cameras, digital video recorders, videoprocessing servers, intrusion detection devices, access control devicesand servers, or other security-related devices.

Still referring to FIG. 4, BMS controller 366 is shown to include acommunications interface 407 and a BMS interface 409. Interface 407 mayfacilitate communications between BMS controller 366 and externalapplications (e.g., monitoring and reporting applications 422,enterprise control applications 426, remote systems and applications444, applications residing on client devices 448, etc.) for allowinguser control, monitoring, and adjustment to BMS controller 366 and/orsubsystems 428. Interface 407 may also facilitate communications betweenBMS controller 366 and client devices 448. BMS interface 409 mayfacilitate communications between BMS controller 366 and buildingsubsystems 428 (e.g., HVAC, lighting security, lifts, powerdistribution, business, etc.).

Interfaces 407 and 409 may be or may include wired or wirelesscommunications interfaces (e.g., jacks, antennas, transmitters,receivers, transceivers, wire terminals, etc.) for conducting datacommunications with building subsystems 428 or other external systems ordevices. In various embodiments, communications via interfaces 407 and409 may be direct (e.g., local wired or wireless communications) or viaa communications network 446 (e.g., a WAN, the Internet, a cellularnetwork, etc.). For example, interfaces 407 and 409 may include anEthernet card and port for sending and receiving data via anEthernet-based communications link or network. In another example,interfaces 407 and 409 may include a WiFi transceiver for communicatingvia a wireless communications network. In another example, one or bothof interfaces 407 and 409 may include cellular or mobile phonecommunications transceivers. In one embodiment, communications interface407 is a power line communications interface and BMS interface 409 is anEthernet interface. In other embodiments, both communications interface407 and BMS interface 409 are Ethernet interfaces or are the sameEthernet interface.

Still referring to FIG. 4, BMS controller 366 is shown to include aprocessing circuit 404 including a processor 406 and memory 408.Processing circuit 404 may be communicably connected to BMS interface409 and/or communications interface 407 such that processing circuit 404and the various components thereof may send and receive data viainterfaces 407 and 409. Processor 406 may be implemented as a generalpurpose processor, an application specific integrated circuit (ASIC),one or more field programmable gate arrays (FPGAs), a group ofprocessing components, or other suitable electronic processingcomponents.

Memory 408 (e.g., memory, memory unit, storage device, etc.) may includeone or more devices (e.g., RAM, ROM, Flash memory, hard disk storage,etc.) for storing data and/or computer code for completing orfacilitating the various processes, layers, and modules described in thepresent application. Memory 408 may be or include volatile memory ornon-volatile memory. Memory 408 may include database components, objectcode components, script components, or any other type of informationstructure for supporting the various activities and informationstructures described in the present application. According to anexemplary embodiment, memory 408 is communicably connected to processor406 via processing circuit 404 and includes computer code for executing(e.g., by processing circuit 404 and/or processor 406) one or moreprocesses described herein.

In some embodiments, BMS controller 366 is implemented within a singlecomputer (e.g., one server, one housing, etc.). In various otherembodiments, BMS controller 366 may be distributed across multipleservers or computers (e.g., that may exist in distributed locations).Further, while FIG. 4 shows applications 422 and 426 as existing outsideof BMS controller 366, in some embodiments, applications 422 and 426 maybe hosted within BMS controller 366 (e.g., within memory 408).

Still referring to FIG. 4, memory 408 is shown to include an enterpriseintegration layer 410, an automated measurement and validation (AM&V)layer 412, a demand response (DR) layer 414, a fault detection anddiagnostics (FDD) layer 416, an integrated control layer 418, and abuilding subsystem integration later 420. Layers 410-420 may beconfigured to receive inputs from building subsystems 428 and other datasources, determine optimal control actions for building subsystems 428based on the inputs, generate control signals based on the optimalcontrol actions, and provide the generated control signals to buildingsubsystems 428. The following paragraphs describe some of the generalfunctions performed by each of layers 410-420 in BMS 400.

Enterprise integration layer 410 may be configured to serve clients orlocal applications with information and services to support a variety ofenterprise-level applications. For example, enterprise controlapplications 426 may be configured to provide subsystem-spanning controlto a graphical user interface (GUI) or to any number of enterprise-levelbusiness applications (e.g., accounting systems, user identificationsystems, etc.). Enterprise control applications 426 may also oralternatively be configured to provide configuration GUIs forconfiguring BMS controller 366. In yet other embodiments, enterprisecontrol applications 426 may work with layers 410-420 to optimizebuilding performance (e.g., efficiency, energy use, comfort, or safety)based on inputs received at interface 407 and/or BMS interface 409.

Building subsystem integration layer 420 may be configured to managecommunications between BMS controller 366 and building subsystems 428.For example, building subsystem integration layer 420 may receive sensordata and input signals from building subsystems 428 and provide outputdata and control signals to building subsystems 428. Building subsystemintegration layer 420 may also be configured to manage communicationsbetween building subsystems 428. Building subsystem integration layer420 translates communications (e.g., sensor data, input signals, outputsignals, etc.) across a plurality of multi-vendor/multi-protocolsystems.

Demand response layer 414 may be configured to optimize resource usage(e.g., electricity use, natural gas use, water use, etc.) and/or themonetary cost of such resource usage in response to satisfy the demandof building 10. The optimization may be based on time-of-use prices,curtailment signals, energy availability, or other data received fromutility providers, distributed energy generation systems 424, fromenergy storage 427 (e.g., hot TES 242, cold TES 244, etc.), or fromother sources. Demand response layer 414 may receive inputs from otherlayers of BMS controller 366 (e.g., building subsystem integration layer420, integrated control layer 418, etc.). The inputs received from otherlayers may include environmental or sensor inputs such as temperature,carbon dioxide levels, relative humidity levels, air quality sensoroutputs, occupancy sensor outputs, room schedules, and the like. Theinputs may also include inputs such as electrical use (e.g., expressedin kWh), thermal load measurements, pricing information, projectedpricing, smoothed pricing, curtailment signals from utilities, and thelike.

According to an exemplary embodiment, demand response layer 414 includescontrol logic for responding to the data and signals it receives. Theseresponses may include communicating with the control algorithms inintegrated control layer 418, changing control strategies, changingsetpoints, or activating/deactivating building equipment or subsystemsin a controlled manner. Demand response layer 414 may also includecontrol logic configured to determine when to utilize stored energy. Forexample, demand response layer 414 may determine to begin using energyfrom energy storage 427 just prior to the beginning of a peak use hour.

In some embodiments, demand response layer 414 includes a control moduleconfigured to actively initiate control actions (e.g., automaticallychanging setpoints) which minimize energy costs based on one or moreinputs representative of or based on demand (e.g., price, a curtailmentsignal, a demand level, etc.). In some embodiments, demand responselayer 414 uses equipment models to determine an optimal set of controlactions. The equipment models may include, for example, thermodynamicmodels describing the inputs, outputs, and/or functions performed byvarious sets of building equipment. Equipment models may representcollections of building equipment (e.g., subplants, chiller arrays,etc.) or individual devices (e.g., individual chillers, heaters, pumps,etc.).

Demand response layer 414 may further include or draw upon one or moredemand response policy definitions (e.g., databases, XML files, etc.).The policy definitions may be edited or adjusted by a user (e.g., via agraphical user interface) so that the control actions initiated inresponse to demand inputs may be tailored for the user's application,desired comfort level, particular building equipment, or based on otherconcerns. For example, the demand response policy definitions mayspecify which equipment may be turned on or off in response toparticular demand inputs, how long a system or piece of equipment shouldbe turned off, what setpoints may be changed, what the allowable setpoint adjustment range is, how long to hold a high demand setpointbefore returning to a normally scheduled setpoint, how close to approachcapacity limits, which equipment modes to utilize, the energy transferrates (e.g., the maximum rate, an alarm rate, other rate boundaryinformation, etc.) into and out of energy storage devices (e.g., thermalstorage tanks, battery banks, etc.), and when to dispatch on-sitegeneration of energy (e.g., via fuel cells, a motor generator set,etc.).

Integrated control layer 418 may be configured to use the data input oroutput of building subsystem integration layer 420 and/or demandresponse later 414 to make control decisions. Due to the subsystemintegration provided by building subsystem integration layer 420,integrated control layer 418 may integrate control activities of thesubsystems 428 such that the subsystems 428 behave as a singleintegrated supersystem. In an exemplary embodiment, integrated controllayer 418 includes control logic that uses inputs and outputs from aplurality of building subsystems to provide greater comfort and energysavings relative to the comfort and energy savings that separatesubsystems could provide alone. For example, integrated control layer418 may be configured to use an input from a first subsystem to make anenergy-saving control decision for a second subsystem. Results of thesedecisions may be communicated back to building subsystem integrationlayer 420.

Integrated control layer 418 is shown to be logically below demandresponse layer 414. Integrated control layer 418 may be configured toenhance the effectiveness of demand response layer 414 by enablingbuilding subsystems 428 and their respective control loops to becontrolled in coordination with demand response layer 414. Thisconfiguration may advantageously reduce disruptive demand responsebehavior relative to conventional systems. For example, integratedcontrol layer 418 may be configured to assure that a demandresponse-driven upward adjustment to the setpoint for chilled watertemperature (or another component that directly or indirectly affectstemperature) does not result in an increase in fan energy (or otherenergy used to cool a space) that would result in greater total buildingenergy use than was saved at the chiller.

Integrated control layer 418 may be configured to provide feedback todemand response layer 414 so that demand response layer 414 checks thatconstraints (e.g., temperature, lighting levels, etc.) are properlymaintained even while demanded load shedding is in progress. Theconstraints may also include setpoint or sensed boundaries relating tosafety, equipment operating limits and performance, comfort, fire codes,electrical codes, energy codes, and the like. Integrated control layer418 is also logically below fault detection and diagnostics layer 416and AM&V layer 412. Integrated control layer 418 may be configured toprovide calculated inputs (e.g., aggregations) to these higher levelsbased on outputs from more than one building subsystem.

AM&V layer 412 may be configured to verify that control strategiescommanded by integrated control layer 418 or demand response layer 414are working properly (e.g., using data aggregated by AM&V layer 412,integrated control layer 418, building subsystem integration layer 420,FDD layer 416, or otherwise). The calculations made by AM&V layer 412may be based on building system energy models and/or equipment modelsfor individual BMS devices or subsystems. For example, AM&V layer 412may compare a model-predicted output with an actual output from buildingsubsystems 428 to determine an accuracy of the model.

FDD layer 416 may be configured to provide on-going fault detection forbuilding subsystems 428, building subsystem devices (i.e., buildingequipment), and control algorithms used by demand response layer 414 andintegrated control layer 418. FDD layer 416 may receive data inputs fromintegrated control layer 418, directly from one or more buildingsubsystems or devices, or from another data source. FDD layer 416 mayautomatically diagnose and respond to detected faults. The responses todetected or diagnosed faults may include providing an alert message to auser, a maintenance scheduling system, or a control algorithm configuredto attempt to repair the fault or to work-around the fault.

FDD layer 416 may be configured to output a specific identification ofthe faulty component or cause of the fault (e.g., loose damper linkage)using detailed subsystem inputs available at building subsystemintegration layer 420. In other exemplary embodiments, FDD layer 416 isconfigured to provide “fault” events to integrated control layer 418which executes control strategies and policies in response to thereceived fault events. According to an exemplary embodiment, FDD layer416 (or a policy executed by an integrated control engine or businessrules engine) may shut-down systems or direct control activities aroundfaulty devices or systems to reduce energy waste, extend equipment life,or assure proper control response.

FDD layer 416 may be configured to store or access a variety ofdifferent system data stores (or data points for live data). FDD layer416 may use some content of the data stores to identify faults at theequipment level (e.g., specific chiller, specific AHU, specific terminalunit, etc.) and other content to identify faults at component orsubsystem levels. For example, building subsystems 428 may generatetemporal (i.e., time-series) data indicating the performance of BMS 400and the various components thereof. The data generated by buildingsubsystems 428 may include measured or calculated values that exhibitstatistical characteristics and provide information about how thecorresponding system or process (e.g., a temperature control process, aflow control process, etc.) is performing in terms of error from itssetpoint. These processes may be examined by FDD layer 416 to exposewhen the system begins to degrade in performance and alert a user torepair the fault before it becomes more severe.

HVAC Actuator

FIG. 5 is a view of an actuator 500 according to an exemplaryembodiment. In some implementations, actuator 500 may be used in HVACsystem 100, waterside system 200, airside system 300, or BMS 400, asdescribed with reference to FIGS. 1-4. For example, actuator 500 may bea damper actuator, a valve actuator, a fan actuator, a pump actuator, orany other type of actuator that may be used in an HVAC system or BMS. Invarious embodiments, actuator 500 may be a linear actuator (e.g., alinear proportional actuator), a non-linear actuator (e.g., a rotaryactuator), a spring return actuator, or a non-spring return actuator.

Actuator 500 is shown to include a housing 502 having a first side 504(e.g., an interior side), and a second side 506 (e.g., an exterior side)opposite the first side 504. Housing 502 may contain the mechanical andprocessing components of actuator 500 when assembled. In someembodiments, housing 502 contains a brushless direct current (BLDC)motor and a processing circuit configured to provide a pulse widthmodulated (PWM) DC output to control the speed of the motor. In otherembodiments, the housing 502 may contain other types of motors that arecontrollable (e.g., by the various processing components of the actuator500 and/or the HVAC or BMS system 100, 400).

Actuator 500 is shown to include a yoke 508. Additionally, the housing502 is shown to include an enclosure 510. The enclosure 510 may be sizedto receive the yoke 508. Yoke 508 may be a rotary yoke 508 or a linearyoke 508, as discussed in further detail below. Each of these yokes 508may be used on corresponding rotary or linear actuators 500.

Referring now to FIG. 6 and FIG. 7, the enclosure 510 may form anopening 600 through the housing 502. Specifically, FIG. 6 shows a viewof the enclosure 510 of the housing, according to an exemplaryembodiment. Additionally, FIG. 7 shows a portion of the enclosure 510 ofthe housing 502, according to an exemplary embodiment. As can be bestseen in FIG. 6, the opening 600 may extend through the housing 502 suchthat the opening 600 may be accessed via the first side 504 or secondside 506 of the housing 502.

The opening 600 may have an interior surface 602. The interior surface602 may be a surface of the enclosure 510 that faces the yoke 508 whenthe yoke/enclosure assembly 508, 510 is assembled.

The enclosure 510 includes a plurality of channels 604 in the interiorsurface 602. The plurality of channels 604 may be radially arrangedabout the enclosure 510. As shown, the channels 604 may extend betweenthe first side 504 and second side 506. The channels 604 may thereforeextend the length of the enclosure 510. The channels 604 may have awidth 606. Some portions of the channel 604 may have a greater widththan other portions of the channel 604. For instance, the channel 604may have a narrower portion near the second side 506 of the housing 502and a wider portion near the first side 504 of the housing 502. A ledgeportion 608 may be formed at the juncture between the narrower portionand the wider portion of the channel 604. Accordingly, the ledge portion608 may be defined by a change in width 606 of the channel 604. Theledge portion 608 may extend partially across the channel 604. The ledgeportion 608 may have a width 610 that that is less than the width 606 ofthe wider portion of channel 604. In some embodiments, the ledge portion608 may have a width 610 that is less than the width 606 of the narrowerportion of the channel 604.

The channels 604 may also have a depth 612. Additionally, the ledgeportion 608 may have a corresponding length 614. The length 614 may be ameasurement from the ledge portion 608 to, for instance, a top 616 ofthe enclosure 510. As described in greater detail below, the width 606,length 514, and depth 612 of features within the channel 604 may bedefined by various characteristics or features on the yoke 508.

In some embodiments, each channel 604 may include a bevel 618. The bevel618 may extend from an end of the ledge portion 608 within the channel604. Accordingly, the bevel 618 smoothen the transition between thenarrower portion of the channel 604 and the wider portion of the channel604.

Referring now to FIGS. 6-8B, various features of the yokes 508 maycorrespond to features described above for the enclosure 510. FIG. 8Ashows a linear yoke 508 for a linear actuator 500, and FIG. 8B shows arotary yoke 508 for a rotary actuator 500.

The yokes 508 shown in FIG. 8A and FIG. 8B include an exterior surface800. The exterior surface 800 of the yoke 508 is an outwardly-facingsurface which faces the interior surface 602 of the enclosure 510 whenassembled. Additionally, the yokes 508 may include a first end 802 and asecond end 804. The first end 802 may face inwardly in the enclosure510, and the second end 804 may face outwardly in the enclosure 510. Thesecond end 804 may engage with a movable HVAC system 100 componentfollowing assembly.

The exterior surface 800 is shown to include a plurality of projections806. The projections 806 may be radially arranged about the exteriorsurface 800. While a plurality of projections 806 are shown, in someembodiments, the exterior surface 800 may include one projection 806.The projections 806 may have a width 808 and length 810.

The width 808 of a projection 806 may correlate to the width 606 of thenarrow portion of the channel 604 for the enclosure 510. For instance,the width 808 may be substantially the same (or slightly less than) thewidth 606 of the channel 604 such that the projection 806 can slidealong the channel 604 during assembly. In some embodiments, the width808 may be substantially the same as the width 610 of the ledge portion608. In these embodiments, the width 610 of the ledge portion 608 isless than the width 606 of the narrow portion of the channel 604.

Additionally, the length 810 may correlate to the length 614 of theledge portion 608. For instance, the length 614 of the projection 806may be substantially the same (or less than) the length 614 from theledge portion 608 to the top 616 of the enclosure 510 that, duringassembly, the projection 806 is flush with (or recessed with respect to)the top 616 of the enclosure 510.

Additionally, the projections 806 may have a thickness 812. Thethickness 812 may correlate to the depth 612 of the channel 604. Forinstance, the thickness 812 may be equal to (or less than) the depth 612of the channel 604.

The projections 806 may be positioned a distance 814 from a base ring816 of the yoke 508. Specifically, a bottom 818 of each projection 806may be located a distance 814 from the base ring 816. The distance 814may correlate to the length of the channel 604. For instance, thedistance 814 may be equal to (or slightly greater than) the length ofthe channel less length 614. In these embodiments, the projections 806may be configured to rest upon the ledge portion 608 with the base ring820 in contact with a bottom 620 of the enclosure 510.

In some embodiments, some projections 806 may have different distances814 than other distances 814. For instance, as can be best seen in FIG.8B, in some embodiments, some projections 806 may be positioned atdifferent distances 814. Such embodiments may ensure proper orientationof the yoke 508 during assembly. Note that, in these embodiments, thechannels 604 may be correspondingly modified.

Referring now to FIG. 9, a locking mechanism 900 for the enclosure 510is shown, according to an exemplary embodiment. The locking mechanism900 is shown to include a ring portion 902 and a plurality of tabs 904.The tabs 904 may be located along one side 906 of the ring portion 902.Each tab may have a corresponding length 908, width 910, and thickness912.

The length 908 of each tab 904 may correlate to the length 614 of theledge portion 608. For instance, the length 908 of each tab 904 may besubstantially the same as the length 614 of the ledge portion 608.

The width 910 of each tab 904 may correlate to the width 606 of thewider portion of the channel 604 and the width 808 of the projections806. For instance, the width 910 of a respective tab 904 may besubstantially the same as the width 606 of the wider portion of thechannel 604 less the width 808 of the projections 806.

The thickness 912 of each tab 904 may correlate to the depth 612 of thechannel 604.

In operation, when the yoke 508 is inserted into one side of theenclosure 510 and properly positioned, the locking mechanism 900 is thenpositioned on the opposite side of the enclosure 510 with the tabs 904adjacent to the respective projections 806. The tabs 904 then preventreverse rotation (or other respective movement) of the yoke 508 withrespect to the enclosure 510.

Assembly of the HVAC Actuator

An example process of assembling the HVAC actuator 500 will be describedwith reference to FIG. 10 and FIG. 11. Specifically, FIG. 10 shows anexploded view of the yoke 508, enclosure 510, and locking mechanism 900assembly. FIG. 11 shows a flowchart of a process 1100 of assembling theHVAC actuator 500.

The process 1100 is shown to include inserting the yoke 508 into a firstopening of the enclosure 510 for the HVAC actuator 500 (step 1102). Thefirst opening may be the opening nearest to the second side 506. Forinstance, the first opening may be the bottom 620 of the enclosure 510.As shown in the exploded view, the first end 802 of the yoke 508 isinserted into the opening located at the bottom 620 of the enclosure510. The yoke 508 may be positioned such that the projections 806 slidealong the channels 604 (e.g., the narrow portion of the channels 604) asthe yoke 508 is inserted into the enclosure 510. In some embodiments,the yoke 508 may be pushed into the enclosure 510 until the base ring820 touches the bottom 620 of the enclosure.

The process 1100 is shown to include rotating the yoke 508 such that theprojection 806 rests upon the ledge portion 608 (step 1104). The yoke508 may be rotated such that the projections 806 rotate within the widerportion of their respective channels 604. The yoke 508 may be rotatedsuch that the projections 806 move from a position where the yoke 508may be removed by sliding the projections 806 back through the channels604 to a position where the yoke 508 may not be removed due torestrictive motion caused by the ledge portion 608.

The process 1100 is shown to include inserting the locking mechanism 900into a second opening of the enclosure 510 (step 1106). The secondopening may be the opening nearest to the first side 504. For instance,the second opening may be the top 616 of the enclosure 510. As shown inthe exploded view, the locking mechanism 900 is oriented with the tabs904 facing downwards towards the enclosure 510. The locking mechanism900 is positioned in the enclosure 510 such that the tabs 904 arepositioned adjacent to the projections 806. The tabs 904 extend into thechannel 604 next to the projections 806. Accordingly, both the tabs 904and the projections 806 may be located within the wider portion of arespective channel 604. Additionally, the width 910 of the tabs 904 andthe width 808 of the projections 806 may combine to equal substantiallythe width 606 of the wider portion of the channel 604 above the ledgeportion 608.

Referring now to FIGS. 12A-12B, cross-sectional views of an assembledactuator 500 are shown, according to exemplary embodiments.Specifically, FIG. 12A shows an assembled linear actuator 500, and FIG.12B shows an assembled rotary actuator 500.

As can be seen in FIG. 12A and FIG. 12B, the yoke 508 is positionedwithin the enclosure 510. Each yoke 508 includes an adaptor 1200 forproviding actuator 500 movement (e.g., linear movement in FIG. 12A, androtational movement in FIG. 12B). The adaptor 1200 is operativelyconnected to a driver 1202, which may be rotated by a motor in theactuator 500. The locking mechanism 900 is positioned within theenclosure 510 as described above (e.g., with the tabs 904 facingdownward and located adjacent to the projections 806 of the yoke 508).The actuator 500 is then controlled to move (e.g., rotational or linearmovement). Additionally, reverse movement or slip of the yoke 508 isinhibited due to the locking mechanism 900.

According to the aspects described herein, the locking mechanism 900 mayinhibit movement of the yoke 508 with respect to the enclosure 510.Additionally, the configuration of the interior surface 602 of theenclosure 510 may be suitable for both rotary and linear yokes 508,thereby potentially saving production costs. Furthermore, the yoke508/enclosure 510/locking mechanism 900 assembly may be relativelysimple to assemble (and disassemble as needed) as compared to other HVACactuators. Lastly, the arrangements described herein may be less likelyto break any of the components described herein during disassembly.

Configuration of Exemplary Embodiments

As utilized herein, the terms “approximately,” “about,” “substantially”,and similar terms are intended to have a broad meaning in harmony withthe common and accepted usage by those of ordinary skill in the art towhich the subject matter of this disclosure pertains. It should beunderstood by those of skill in the art who review this disclosure thatthese terms are intended to allow a description of certain featuresdescribed and claimed without restricting the scope of these features tothe precise numerical ranges provided. Accordingly, these terms shouldbe interpreted as indicating that insubstantial or inconsequentialmodifications or alterations of the subject matter described and claimedare considered to be within the scope of the disclosure as recited inthe appended claims.

It should be noted that the term “exemplary” and variations thereof, asused herein to describe various embodiments, are intended to indicatethat such embodiments are possible examples, representations, orillustrations of possible embodiments (and such terms are not intendedto connote that such embodiments are necessarily extraordinary orsuperlative examples).

The term “coupled” and variations thereof, as used herein, means thejoining of two members directly or indirectly to one another. Suchjoining may be stationary (e.g., permanent or fixed) or moveable (e.g.,removable or releasable). Such joining may be achieved with the twomembers coupled directly to each other, with the two members coupled toeach other using a separate intervening member and any additionalintermediate members coupled with one another, or with the two memberscoupled to each other using an intervening member that is integrallyformed as a single unitary body with one of the two members. If“coupled” or variations thereof are modified by an additional term(e.g., directly coupled), the generic definition of “coupled” providedabove is modified by the plain language meaning of the additional term(e.g., “directly coupled” means the joining of two members without anyseparate intervening member), resulting in a narrower definition thanthe generic definition of “coupled” provided above. Such coupling may bemechanical, electrical, or fluidic.

The term “or,” as used herein, is used in its inclusive sense (and notin its exclusive sense) so that when used to connect a list of elements,the term “or” means one, some, or all of the elements in the list.Conjunctive language such as the phrase “at least one of X, Y, and Z,”unless specifically stated otherwise, is understood to convey that anelement may be either X, Y, Z; X and Y; X and Z; Y and Z; or X, Y, and Z(i.e., any combination of X, Y, and Z). Thus, such conjunctive languageis not generally intended to imply that certain embodiments require atleast one of X, at least one of Y, and at least one of Z to each bepresent, unless otherwise indicated.

References herein to the positions of elements (e.g., “top,” “bottom,”“above,” “below”) are merely used to describe the orientation of variouselements in the FIGURES. It should be noted that the orientation ofvarious elements may differ according to other exemplary embodiments,and that such variations are intended to be encompassed by the presentdisclosure.

Although the figures and description may illustrate a specific order ofmethod steps, the order of such steps may differ from what is depictedand described, unless specified differently above. Also, two or moresteps may be performed concurrently or with partial concurrence, unlessspecified differently above. Such variation may depend, for example, onthe software and hardware systems chosen and on designer choice. Allsuch variations are within the scope of the disclosure. Likewise,software implementations of the described methods could be accomplishedwith standard programming techniques with rule-based logic and otherlogic to accomplish the various connection steps, processing steps,comparison steps, and decision steps.

It is important to note that the construction and arrangement of theHVAC actuator and assembly thereof as shown in the various exemplaryembodiments is illustrative only. Additionally, any element disclosed inone embodiment may be incorporated or utilized with any other embodimentdisclosed herein.

What is claimed is:
 1. An actuator, comprising: a housing comprising an enclosure having an interior surface including a channel with a ledge portion extending through the enclosure; a yoke having a notch located on an external surface, the yoke positioned in the enclosure with the notch resting on the ledge portion of the enclosure; a locking mechanism including a ring having a tab with a width defined by a width of the channel and a width of the notch, the locking mechanism positioned on an opposite side of the enclosure with the tab positioned in the channel adjacent to the notch and thereby inhibiting reverse rotation of the yoke.
 2. The actuator of claim 1, wherein the actuator is a rotary actuator.
 3. The actuator of claim 1, wherein the actuator is a linear actuator.
 4. The actuator of claim 1, wherein: the enclosure includes a plurality of channels extending therethrough, each of the plurality of channels including corresponding ledge portions; the yoke has a plurality of notches on the external surface; the ring of the locking mechanism has a plurality of tabs; and each of the plurality of notches rests upon one of the ledge portions, and each of the plurality of tabs is located in a respective channel of the plurality of channels and adjacent to a respective notch of the plurality of notches.
 5. The actuator of claim 4, wherein the plurality of channels are radially arranged about the enclosure.
 6. The actuator of claim 1, wherein the width of the channel at the ledge portion is equal to, at least, the width of the width of the tab and the width of the notch.
 7. The actuator of claim 1, wherein the channel has a narrow portion and a wide portion, wherein the ledge portion is located within the wide portion of the channel.
 8. The actuator of claim 7, wherein the yoke is inserted in the enclosure with the notch at the narrow portion and pushed to the wide portion, and wherein the yoke is rotated when the notch is located at the wide portion to rest upon the ledge portion.
 9. The actuator of claim 8, wherein the locking mechanism is inserted with the tab at the wide portion where the tab is located adjacent to the notch.
 10. An actuator, comprising: a housing comprising an enclosure having an interior surface including a plurality of channels with corresponding ledge portions, the plurality of channels extending through the enclosure; a yoke having a plurality of notches located on an external surface, the yoke positioned in the enclosure with the notches resting on respective ledge portions of the enclosure; a locking mechanism including a ring having a plurality of tabs with a width defined by a width of the channel and a width of the notch, the locking mechanism positioned on an opposite side of the enclosure with the tabs positioned in respective channels adjacent to respective notches and thereby inhibiting reverse rotation of the yoke.
 11. The actuator of claim 10, wherein the actuator is a rotary actuator.
 12. The actuator of claim 10, wherein the actuator is a linear actuator.
 13. The actuator of claim 10, wherein the plurality of channels are radially arranged about the enclosure.
 14. The actuator of claim 10, wherein the width of the channels at the ledge portion is equal to, at least, the width of the width of the tabs and the width of the notches.
 15. The actuator of claim 10, wherein the channels have a narrow portion and a wide portion, wherein the ledge portion is located within the wide portion of the channel.
 16. The actuator of claim 15, wherein the yoke is inserted in the enclosure with the notches at the narrow portion and pushed to the wide portion, and wherein the yoke is rotated when the notches are located at the wide portion to rest upon the ledge.
 17. The actuator of claim 16, wherein the locking mechanism is inserted with the tabs at the wide portion where the tabs located adjacent to the notch.
 18. A method of assembling an actuator, the method comprising: inserting a yoke into a first opening of an enclosure for an actuator, wherein the enclosure includes an interior surface having a channel with a ledge portion extending through the enclosure, and wherein the yoke has a notch on an external surface facing the channel when the yoke is inserted into the first opening; rotating the yoke such that the notch rests on the ledge portion of the enclosure; and inserting a locking mechanism into a second opening of the enclosure, wherein the locking mechanism includes a tab having a width corresponding to a width of the channel and a width of the notch, and wherein the tab is positioned in the channel adjacent to the notch thereby inhibiting movement of the yoke with respect to the enclosure.
 19. The method of claim 18, wherein the channel has a narrow portion and a wide portion with the ledge portion being located within the wide portion of the channel, and wherein inserting the yoke into the first opening comprises: inserting the yoke into the first opening of the enclosure for the actuator adjacent to the narrow portion; and pushing the yoke into the enclosure such that the notch moves from the narrow portion to the wide portion, and wherein the yoke is rotated when the notch is located within the wide portion.
 20. The method of claim 19, wherein the locking mechanism is inserted with the tab at the wide portion where the tab is located adjacent to the notch. 